CodSpeed Performance Report

Merging #9851 will not alter performance

_{Comparing chunk_parsing_fix (1cd18c3) with master (a9a0d84)}

Summary

✅ 24 untouched benchmarks

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.70%. Comparing base (a9a0d84) to head (1cd18c3).
Report is 656 commits behind head on master.

✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##           master    #9851   +/-   ##
=======================================
  Coverage   98.70%   98.70%           
=======================================
  Files         118      118           
  Lines       36261    36278   +17     
  Branches     4311     4314    +3     
=======================================
+ Hits        35793    35810   +17     
  Misses        315      315           
  Partials      153      153           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Backport to 3.10: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 541d86d on top of patchback/backports/3.10/541d86d9e7884590c655876cd40042565293d8df/pr-9851

Backporting merged PR #9851 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.10/541d86d9e7884590c655876cd40042565293d8df/pr-9851 upstream/3.10

4. Now, cherry-pick PR Fix incorrect parsing of chunk extensions with the pure Python parser #9851 contents into that branch:

   $ git cherry-pick -x 541d86d9e7884590c655876cd40042565293d8df

   If it'll yell at you with something like fatal: Commit 541d86d9e7884590c655876cd40042565293d8df is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 541d86d9e7884590c655876cd40042565293d8df

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix incorrect parsing of chunk extensions with the pure Python parser #9851 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/541d86d9e7884590c655876cd40042565293d8df/pr-9851

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

Backport to 3.11: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 541d86d on top of patchback/backports/3.11/541d86d9e7884590c655876cd40042565293d8df/pr-9851

Backporting merged PR #9851 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.11/541d86d9e7884590c655876cd40042565293d8df/pr-9851 upstream/3.11

4. Now, cherry-pick PR Fix incorrect parsing of chunk extensions with the pure Python parser #9851 contents into that branch:

   $ git cherry-pick -x 541d86d9e7884590c655876cd40042565293d8df

   If it'll yell at you with something like fatal: Commit 541d86d9e7884590c655876cd40042565293d8df is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 541d86d9e7884590c655876cd40042565293d8df

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix incorrect parsing of chunk extensions with the pure Python parser #9851 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/541d86d9e7884590c655876cd40042565293d8df/pr-9851

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.